3.1.3.2. iCalender Client 2

The client went through a number of the iMip tests between their client and another iCalendar client. The following issues were spotted during that and also during client testing originated by other companies.

• An original All day event sent in a UK timezone ended up with time shifted to a specific California timezone.

• iCalendar sent on behalf of another user did not correctly specify this in the ORGANIZER, although the MIME Sender: and From: headers were correct.

• Canceled messages from other server ended up with 2 iCAL “STATUS:CANCELED” entries (not in the original)

• Meeting acceptances and cancelled meetings from a server caused problems with incoming internet gateway.

• An initial meeting request will often have a sequence number of 1, which another client considers to be an update.

• Sequence numbers in Exceptions were not being updated when changes were made to them.

• One client discovered an issue where a cache of information for appointments was not being updated when changes were made. This showed up when 2 clients were accessing the same calendar, which may be quite a useful testing methodology as iCalendar. App’s own caching behaviour hides this bug in the originating client.

• Thanks for all your work